Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't reset unread count when adding a synthetic receipt #3706

Merged

Conversation

andybalaam
Copy link
Member

@andybalaam andybalaam commented Sep 6, 2023

Fixes #3684 and there are lots more details about why we chose this solution in that issue.


Here's what your changelog entry will look like:

🐛 Bug Fixes

Fixes #3684
and there are lots more details about why we chose this solution in that
issue.
Copy link
Contributor

@weeman1337 weeman1337 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. 👍 I don't know all of the read receipt details. But implementation matches the comment from here.

@andybalaam andybalaam added this pull request to the merge queue Sep 7, 2023
@andybalaam
Copy link
Member Author

I would say we are not 100% confident on this change, which is why we are merging soon after the RC was cut. All the tests that we have are passing, but we don't feel they cover all the cases yet. When element-hq/element-web#25449 is done, we should be more confident.

Merged via the queue into develop with commit 0700e86 Sep 7, 2023
24 of 25 checks passed
@andybalaam andybalaam deleted the andybalaam/dont-reset-unread-on-synthetic-receipt branch September 7, 2023 07:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Notification counts may be incorrectly reset by sent messages
2 participants